Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6522c6a1bc32576a3b23b1c5d32bb34b1b5b5f58dd32d3e56438f4b257733eb0

Tx prefix hash: b5046a243c3ec8d09fc97aa58f23ec3e6c3f2a015a2e67d65fef5d6009e2c086
Tx public key: 1b6cb166b29294b9f3065a8e802b39ab13f8780cc458a9f7014f8182517ca30e
Timestamp: 1737178151 Timestamp [UCT]: 2025-01-18 05:29:11 Age [y:d:h:m:s]: 00:058:06:59:11
Block: 1199823 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41446 RingCT/type: yes/0
Extra: 011b6cb166b29294b9f3065a8e802b39ab13f8780cc458a9f7014f8182517ca30e021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e87394885f0ef10f9e5e4e4795a8344167cfdb4448d6e2cef624cb8eed1ba0c5 0.600000000000 1686456 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": 1199833, "vin": [ { "gen": { "height": 1199823 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e87394885f0ef10f9e5e4e4795a8344167cfdb4448d6e2cef624cb8eed1ba0c5" } } ], "extra": [ 1, 27, 108, 177, 102, 178, 146, 148, 185, 243, 6, 90, 142, 128, 43, 57, 171, 19, 248, 120, 12, 196, 88, 169, 247, 1, 79, 129, 130, 81, 124, 163, 14, 2, 17, 0, 0, 0, 1, 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