Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3d40d8ffd28c3a4739d40d02ab1f0cf2a157c496c13cf16f4c351aea1f95e43

Tx prefix hash: b3afbcb2a6079984e888b7e0b56fdf66d3bbafbcacd8265989701667efe910e4
Tx public key: 1f59482f0f0119ab568f58b9f68f4965f920f3cc636c62fd2fbdd3f691fd09db
Timestamp: 1713732118 Timestamp [UCT]: 2024-04-21 20:41:58 Age [y:d:h:m:s]: 01:207:21:38:30
Block: 1005583 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 407244 RingCT/type: yes/0
Extra: 011f59482f0f0119ab568f58b9f68f4965f920f3cc636c62fd2fbdd3f691fd09db0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9536ec6754534b27b71e906f4f17f3a2b17d5eb7ffb0ce5b2c4ad71ba1a7cc30 0.600000000000 1466321 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": 1005593, "vin": [ { "gen": { "height": 1005583 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9536ec6754534b27b71e906f4f17f3a2b17d5eb7ffb0ce5b2c4ad71ba1a7cc30" } } ], "extra": [ 1, 31, 89, 72, 47, 15, 1, 25, 171, 86, 143, 88, 185, 246, 143, 73, 101, 249, 32, 243, 204, 99, 108, 98, 253, 47, 189, 211, 246, 145, 253, 9, 219, 2, 17, 0, 0, 0, 2, 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