Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e41e4cec5e5d5a23a2e59d89dded4e5907ed4466e881da1e0876e2af7b8952f

Tx prefix hash: 5900dfa68768b6231a57c1d619f96b30269bd0277866163d2e9485168b27e3c8
Tx public key: 41b79c29a859d0375db9573e5d0c1aa97f25ee1683acfd42340f00d969febf2d
Timestamp: 1710188085 Timestamp [UCT]: 2024-03-11 20:14:45 Age [y:d:h:m:s]: 00:349:10:19:01
Block: 976222 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249812 RingCT/type: yes/0
Extra: 0141b79c29a859d0375db9573e5d0c1aa97f25ee1683acfd42340f00d969febf2d0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3c5134d2f437312abf10ebd02e17aff6e1437e3fef0585db0cf2d479d19e18ee 0.600000000000 1436213 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": 976232, "vin": [ { "gen": { "height": 976222 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c5134d2f437312abf10ebd02e17aff6e1437e3fef0585db0cf2d479d19e18ee" } } ], "extra": [ 1, 65, 183, 156, 41, 168, 89, 208, 55, 93, 185, 87, 62, 93, 12, 26, 169, 127, 37, 238, 22, 131, 172, 253, 66, 52, 15, 0, 217, 105, 254, 191, 45, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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