Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b537ff38f8e370145f1a507d6a059c5082c0b925868922121733fdd70302469f

Tx prefix hash: ae741445023bfc98605b4be01b2ad8d690db31ab495d2a18a879166ac18d857a
Tx public key: 08ae89d663f2b1f28b046ae3f3213a13ccad4535bd09cff5f6549048a0d63f6e
Timestamp: 1737952089 Timestamp [UCT]: 2025-01-27 04:28:09 Age [y:d:h:m:s]: 00:141:13:52:18
Block: 1205992 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101121 RingCT/type: yes/0
Extra: 0108ae89d663f2b1f28b046ae3f3213a13ccad4535bd09cff5f6549048a0d63f6e0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 16845f3724d9113c7eb066986d5fdd0de0dc3140f073a9ec131d3d7f3efc5cd3 0.600000000000 1692693 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": 1206002, "vin": [ { "gen": { "height": 1205992 } } ], "vout": [ { "amount": 600000000, "target": { "key": "16845f3724d9113c7eb066986d5fdd0de0dc3140f073a9ec131d3d7f3efc5cd3" } } ], "extra": [ 1, 8, 174, 137, 214, 99, 242, 177, 242, 139, 4, 106, 227, 243, 33, 58, 19, 204, 173, 69, 53, 189, 9, 207, 245, 246, 84, 144, 72, 160, 214, 63, 110, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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