Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfd512700a17804769e4def35bb4828a0db13c4aa6ac7ab81bee2459cc6849e5

Tx prefix hash: 6a679691de4e1eb4660a609d3b13045053a43c7304d5a5b24de1d04bb5f49d39
Tx public key: 00e1b6be55fdb57010e4afe1612bf07841902f029dfe2bd6f34dd539d0c13d9b
Timestamp: 1721081589 Timestamp [UCT]: 2024-07-15 22:13:09 Age [y:d:h:m:s]: 00:178:17:09:33
Block: 1066536 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127862 RingCT/type: yes/0
Extra: 0100e1b6be55fdb57010e4afe1612bf07841902f029dfe2bd6f34dd539d0c13d9b02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cde6386aa710d0172f577b7e23a5e69d6404e320ebd63908f2fe49ac2e2f786f 0.600000000000 1537191 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": 1066546, "vin": [ { "gen": { "height": 1066536 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cde6386aa710d0172f577b7e23a5e69d6404e320ebd63908f2fe49ac2e2f786f" } } ], "extra": [ 1, 0, 225, 182, 190, 85, 253, 181, 112, 16, 228, 175, 225, 97, 43, 240, 120, 65, 144, 47, 2, 157, 254, 43, 214, 243, 77, 213, 57, 208, 193, 61, 155, 2, 17, 0, 0, 0, 3, 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