Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7cc13b668b87be1143d9718fa1cfba1ab31e6468492e08fc5d15e430194f0be7

Tx prefix hash: 6467c4dfc57c57085de2dab9ac1e674bbc54d2ddf6e418bbd720db1e6c47f6e5
Tx public key: d64b4f2827f911ae506fc5e5ee8298802ac2650881300fbbec022e63a99601b9
Timestamp: 1722645395 Timestamp [UCT]: 2024-08-03 00:36:35 Age [y:d:h:m:s]: 00:267:23:22:57
Block: 1079485 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191443 RingCT/type: yes/0
Extra: 01d64b4f2827f911ae506fc5e5ee8298802ac2650881300fbbec022e63a99601b902110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3783d3bc3afd12a7c6d38612df5d76ce5e459d75a73fdaf69aae13f6ff62e0e0 0.600000000000 1552456 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": 1079495, "vin": [ { "gen": { "height": 1079485 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3783d3bc3afd12a7c6d38612df5d76ce5e459d75a73fdaf69aae13f6ff62e0e0" } } ], "extra": [ 1, 214, 75, 79, 40, 39, 249, 17, 174, 80, 111, 197, 229, 238, 130, 152, 128, 42, 194, 101, 8, 129, 48, 15, 187, 236, 2, 46, 99, 169, 150, 1, 185, 2, 17, 0, 0, 0, 10, 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