Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 5ab28a7d4eccc62a0035c5c1dd110a71b027338f2b55e34690ccbee576ff9bf5

Tx prefix hash: 5673ecc6d8bc2a4797ca173e0d331645b726c4702e38a8b51a84dab9ccc47a72
Tx public key: 1b75de7284797b4f3d97efb5c9ee68e50e0a6a8bcae46f91bd7485cfdbfa88fe
Timestamp: 1728260726 Timestamp [UCT]: 2024-10-07 00:25:26 Age [y:d:h:m:s]: 00:159:22:50:31
Block: 1126043 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114127 RingCT/type: yes/0
Extra: 011b75de7284797b4f3d97efb5c9ee68e50e0a6a8bcae46f91bd7485cfdbfa88fe02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3166885f230e55fc4d52ee8f33dc86fe3ac669a4389e077118278718f23ab83e 0.600000000000 1608816 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1126053, "vin": [ { "gen": { "height": 1126043 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3166885f230e55fc4d52ee8f33dc86fe3ac669a4389e077118278718f23ab83e" } } ], "extra": [ 1, 27, 117, 222, 114, 132, 121, 123, 79, 61, 151, 239, 181, 201, 238, 104, 229, 14, 10, 106, 139, 202, 228, 111, 145, 189, 116, 133, 207, 219, 250, 136, 254, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8