Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8849a10415759fc870af9e40264257157f76e48217b44ff94764b544c2bbbf8a

Tx prefix hash: 883aa2667aec66ad70589ff63d30fbb4ea619bc0d2fad3b4f77943d0eb58c555
Tx public key: 014b40bc3ae9656af1b492ad1d1058f213cc1b54f6c2db11f08eb813b110705e
Timestamp: 1718681761 Timestamp [UCT]: 2024-06-18 03:36:01 Age [y:d:h:m:s]: 01:001:08:47:02
Block: 1046626 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261718 RingCT/type: yes/0
Extra: 01014b40bc3ae9656af1b492ad1d1058f213cc1b54f6c2db11f08eb813b110705e0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2b8c5fc531254e243a3812dd2ae90b69dd432f2a40e594d54e3d73576d1b2d0e 0.600000000000 1516443 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": 1046636, "vin": [ { "gen": { "height": 1046626 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b8c5fc531254e243a3812dd2ae90b69dd432f2a40e594d54e3d73576d1b2d0e" } } ], "extra": [ 1, 1, 75, 64, 188, 58, 233, 101, 106, 241, 180, 146, 173, 29, 16, 88, 242, 19, 204, 27, 84, 246, 194, 219, 17, 240, 142, 184, 19, 177, 16, 112, 94, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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