Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6c1b8724850ef7f7c0b2ab1499ad04e5a02c629c402beba3e45296e68339556

Tx prefix hash: f50612e16c9d332fb1078070052e440422c391de8ee9567bbe3cb8ccf0cad14e
Tx public key: 411e2cf7de5562890d0964bfc18be0493ef34d030da4d8d2ff9d69da8f6de410
Timestamp: 1634761814 Timestamp [UCT]: 2021-10-20 20:30:14 Age [y:d:h:m:s]: 03:068:02:04:58
Block: 356999 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 826880 RingCT/type: yes/0
Extra: 01411e2cf7de5562890d0964bfc18be0493ef34d030da4d8d2ff9d69da8f6de4100211000000048d0de867000000000000000000

1 output(s) for total of 40.282324996000 dcy

stealth address amount amount idx
00: 39be0eb9d161b7d280f2be60bd3d223ab2d63abf273d54045e18fa9ed6260d4e 40.282324996000 728141 of 0

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": 357009, "vin": [ { "gen": { "height": 356999 } } ], "vout": [ { "amount": 40282324996, "target": { "key": "39be0eb9d161b7d280f2be60bd3d223ab2d63abf273d54045e18fa9ed6260d4e" } } ], "extra": [ 1, 65, 30, 44, 247, 222, 85, 98, 137, 13, 9, 100, 191, 193, 139, 224, 73, 62, 243, 77, 3, 13, 164, 216, 210, 255, 157, 105, 218, 143, 109, 228, 16, 2, 17, 0, 0, 0, 4, 141, 13, 232, 103, 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