Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef74bb3ba5096049dd6d2873bebddb3b787712ee87b99b7338fdec5e2ff7c50e

Tx prefix hash: a7235dc5d9e96122ba03fb49c32ae717b21d1e0777a9c3f6a33b98f528d4bb54
Tx public key: 42561ec2d3185aacefc6f7c226cf60350a7f5c37b11f7042e08b5287440ceff8
Timestamp: 1745590565 Timestamp [UCT]: 2025-04-25 14:16:05 Age [y:d:h:m:s]: 00:251:08:45:45
Block: 1269207 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177423 RingCT/type: yes/0
Extra: 0142561ec2d3185aacefc6f7c226cf60350a7f5c37b11f7042e08b5287440ceff8021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb2eb9bc542115d7a20d800f75c5e09d2afe7a6b2b2d1a407301bd7761144105 0.600000000000 1756442 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": 1269217, "vin": [ { "gen": { "height": 1269207 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb2eb9bc542115d7a20d800f75c5e09d2afe7a6b2b2d1a407301bd7761144105" } } ], "extra": [ 1, 66, 86, 30, 194, 211, 24, 90, 172, 239, 198, 247, 194, 38, 207, 96, 53, 10, 127, 92, 55, 177, 31, 112, 66, 224, 139, 82, 135, 68, 12, 239, 248, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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