Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa3815535eccf588077810dd559b1af5669b767a791bd51ddbdf2d26e79bf7df

Tx prefix hash: 31c534f531d910fd304907f96fa9319eada9d0d3296cb9b2eb8ea74e234d4014
Tx public key: 47c75f509cbb66ffaf30af7a0b7ad20eab3c1130b4c9e5753f608198f7b3a24e
Timestamp: 1735711062 Timestamp [UCT]: 2025-01-01 05:57:42 Age [y:d:h:m:s]: 00:092:03:04:53
Block: 1187667 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65632 RingCT/type: yes/0
Extra: 0147c75f509cbb66ffaf30af7a0b7ad20eab3c1130b4c9e5753f608198f7b3a24e021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8120f0a767e28048466063d107e9498687f444171aac7a93ef7a82e241b227e1 0.600000000000 1674160 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": 1187677, "vin": [ { "gen": { "height": 1187667 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8120f0a767e28048466063d107e9498687f444171aac7a93ef7a82e241b227e1" } } ], "extra": [ 1, 71, 199, 95, 80, 156, 187, 102, 255, 175, 48, 175, 122, 11, 122, 210, 14, 171, 60, 17, 48, 180, 201, 229, 117, 63, 96, 129, 152, 247, 179, 162, 78, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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