Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54ef54829445f4c63051157fdb1931990043ae8569a91a6f6c6243a3f759e4e2

Tx prefix hash: 2542d35ffea402c3e8cb885d20faa7cec65814e276195d81f1d3f30d019f64c3
Tx public key: 6ff9179437fc72416db6a2be2e53ca8d3aa3fe3c91066cecccb01b468ce7c91e
Timestamp: 1736959321 Timestamp [UCT]: 2025-01-15 16:42:01 Age [y:d:h:m:s]: 00:153:03:19:40
Block: 1197996 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109174 RingCT/type: yes/0
Extra: 016ff9179437fc72416db6a2be2e53ca8d3aa3fe3c91066cecccb01b468ce7c91e0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e26cc28c4c480695bb6da6ccfc8e4371d0528878a332586d27ccbc2e47877b91 0.600000000000 1684613 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": 1198006, "vin": [ { "gen": { "height": 1197996 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e26cc28c4c480695bb6da6ccfc8e4371d0528878a332586d27ccbc2e47877b91" } } ], "extra": [ 1, 111, 249, 23, 148, 55, 252, 114, 65, 109, 182, 162, 190, 46, 83, 202, 141, 58, 163, 254, 60, 145, 6, 108, 236, 204, 176, 27, 70, 140, 231, 201, 30, 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