Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91b42372d17658ef260468f9cb51554fdf591f50f7754d45ff7ef181a6ad45e5

Tx prefix hash: 467135d0103c2632684610af6b837247add872f5886b3dac54ca9890735ae535
Tx public key: 3cd0a1fb25bf4a410126e293bcf264a87d2cee90d950755d2e7d1c876dd5f285
Timestamp: 1721362847 Timestamp [UCT]: 2024-07-19 04:20:47 Age [y:d:h:m:s]: 00:097:10:02:03
Block: 1068866 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69733 RingCT/type: yes/0
Extra: 013cd0a1fb25bf4a410126e293bcf264a87d2cee90d950755d2e7d1c876dd5f28502110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 753d4e22eba555feb5896838a77bb54aabdcd1c309a8b436ad0bce4a721ae5e4 0.600000000000 1540063 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": 1068876, "vin": [ { "gen": { "height": 1068866 } } ], "vout": [ { "amount": 600000000, "target": { "key": "753d4e22eba555feb5896838a77bb54aabdcd1c309a8b436ad0bce4a721ae5e4" } } ], "extra": [ 1, 60, 208, 161, 251, 37, 191, 74, 65, 1, 38, 226, 147, 188, 242, 100, 168, 125, 44, 238, 144, 217, 80, 117, 93, 46, 125, 28, 135, 109, 213, 242, 133, 2, 17, 0, 0, 0, 8, 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