Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b20e0539238ac157d2a2a760e48f48f463fbf52deace73f873878b3845160d83

Tx prefix hash: 1d7598e0150c0a4207334a9dc6cda154fca01eff9fcc8d2d88a7d10d10b87572
Tx public key: 3328691f192d8ac9a8e78d963bb7006c054e1dfb8b3c55d68bc03550c5d0bf77
Timestamp: 1737754624 Timestamp [UCT]: 2025-01-24 21:37:04 Age [y:d:h:m:s]: 00:144:01:21:50
Block: 1204546 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102700 RingCT/type: yes/0
Extra: 013328691f192d8ac9a8e78d963bb7006c054e1dfb8b3c55d68bc03550c5d0bf77021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 33171c1cef4983176bc384d9e31b41d4825fd9a7d8619f0ad6ace3e10f91d456 0.600000000000 1691233 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": 1204556, "vin": [ { "gen": { "height": 1204546 } } ], "vout": [ { "amount": 600000000, "target": { "key": "33171c1cef4983176bc384d9e31b41d4825fd9a7d8619f0ad6ace3e10f91d456" } } ], "extra": [ 1, 51, 40, 105, 31, 25, 45, 138, 201, 168, 231, 141, 150, 59, 183, 0, 108, 5, 78, 29, 251, 139, 60, 85, 214, 139, 192, 53, 80, 197, 208, 191, 119, 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