Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e358e9a9333d1d9bc34fabe82c31421e0a330509f505e0d829224b65daafbf3e

Tx prefix hash: 2ebf852e83afc98900bb790503d5f3feb94fc6a274206bc87a79ae200cc01064
Tx public key: 63252c8870ae834e97a4e55c0fb0aab56bce2a221683ca9ebcfe367d23fa8880
Timestamp: 1726366221 Timestamp [UCT]: 2024-09-15 02:10:21 Age [y:d:h:m:s]: 00:281:21:10:07
Block: 1110328 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201096 RingCT/type: yes/0
Extra: 0163252c8870ae834e97a4e55c0fb0aab56bce2a221683ca9ebcfe367d23fa8880021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 108648fb3f20c62b4d0a1f683907ccf54d802dfa4d49b1b1a45fb7b94c1ea073 0.600000000000 1588893 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": 1110338, "vin": [ { "gen": { "height": 1110328 } } ], "vout": [ { "amount": 600000000, "target": { "key": "108648fb3f20c62b4d0a1f683907ccf54d802dfa4d49b1b1a45fb7b94c1ea073" } } ], "extra": [ 1, 99, 37, 44, 136, 112, 174, 131, 78, 151, 164, 229, 92, 15, 176, 170, 181, 107, 206, 42, 34, 22, 131, 202, 158, 188, 254, 54, 125, 35, 250, 136, 128, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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