Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 405e5a1e80940dafc6ba081a776c13c3e068df047196d1e4afaf81fd0c607c6e

Tx prefix hash: ecbba451324d3a157e3f68e6a3347e424daea3c8a1ee13376c4f8ee19074cff1
Tx public key: 8fdd0b02753912dba3995d4d64a2931595c7937e51e4bc3e1485a43931d754e7
Timestamp: 1737665391 Timestamp [UCT]: 2025-01-23 20:49:51 Age [y:d:h:m:s]: 00:144:19:52:31
Block: 1203810 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103262 RingCT/type: yes/0
Extra: 018fdd0b02753912dba3995d4d64a2931595c7937e51e4bc3e1485a43931d754e7021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 52f1b9332bb3ba278474c601a34053b668e0debc4393a4b7aec0def4306bfd35 0.600000000000 1690489 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": 1203820, "vin": [ { "gen": { "height": 1203810 } } ], "vout": [ { "amount": 600000000, "target": { "key": "52f1b9332bb3ba278474c601a34053b668e0debc4393a4b7aec0def4306bfd35" } } ], "extra": [ 1, 143, 221, 11, 2, 117, 57, 18, 219, 163, 153, 93, 77, 100, 162, 147, 21, 149, 199, 147, 126, 81, 228, 188, 62, 20, 133, 164, 57, 49, 215, 84, 231, 2, 17, 0, 0, 0, 4, 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