Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c37712873c5f1099ec07a55eccac4dc55cc71c9ca8f13bdc2dfb4339719a425c

Tx prefix hash: 132d9caa9c567d2330c7e536940c41cf4ba1c8d242e98c9c1d50e799800c2175
Tx public key: e9c7e2d4f12abac6360bdd45eed26184f5d729187ce7c70ad98ffd883478f9f8
Timestamp: 1742730453 Timestamp [UCT]: 2025-03-23 11:47:33 Age [y:d:h:m:s]: 00:254:20:22:18
Block: 1245529 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179895 RingCT/type: yes/0
Extra: 01e9c7e2d4f12abac6360bdd45eed26184f5d729187ce7c70ad98ffd883478f9f8021100000009af845649000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9ed29141c52ce6a9a41b952a63853231a107850fc929c5f817f490501833c4b 0.600000000000 1732520 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": 1245539, "vin": [ { "gen": { "height": 1245529 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9ed29141c52ce6a9a41b952a63853231a107850fc929c5f817f490501833c4b" } } ], "extra": [ 1, 233, 199, 226, 212, 241, 42, 186, 198, 54, 11, 221, 69, 238, 210, 97, 132, 245, 215, 41, 24, 124, 231, 199, 10, 217, 143, 253, 136, 52, 120, 249, 248, 2, 17, 0, 0, 0, 9, 175, 132, 86, 73, 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