Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e98e33ae1b82d6908b2b0e6ebe8df2009842886b62b8d5d7a251e83b52ed2cf8

Tx prefix hash: 63934b6f555810161fbbf1b00035c94642b45cae9767fbf1b335cfadb917bac0
Tx public key: 4197a0a662a0f5d559f10490d0aebe435eea7af33e583d0509c91e49966dc9ba
Timestamp: 1717435844 Timestamp [UCT]: 2024-06-03 17:30:44 Age [y:d:h:m:s]: 00:311:18:31:25
Block: 1036310 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 222819 RingCT/type: yes/0
Extra: 014197a0a662a0f5d559f10490d0aebe435eea7af33e583d0509c91e49966dc9ba0211000000030cce0636000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb0c60a0f2cce19adfb99e09cdb4608cc585582672a2ec48f9ed09cde1e181f2 0.600000000000 1504835 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": 1036320, "vin": [ { "gen": { "height": 1036310 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb0c60a0f2cce19adfb99e09cdb4608cc585582672a2ec48f9ed09cde1e181f2" } } ], "extra": [ 1, 65, 151, 160, 166, 98, 160, 245, 213, 89, 241, 4, 144, 208, 174, 190, 67, 94, 234, 122, 243, 62, 88, 61, 5, 9, 201, 30, 73, 150, 109, 201, 186, 2, 17, 0, 0, 0, 3, 12, 206, 6, 54, 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