Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2f506ba6554e460a35bbfa6bf8d8bd9b4caf54b0af496f16609c60e461dfa91

Tx prefix hash: 15feb3e0a13d925bee91bddddada1cc27ed025980ef1d7983d8474a0c5e6128b
Tx public key: f438add11e4d27128c4b91986e13aba657f303c34ef2a7990290758d2c8d8d24
Timestamp: 1737733019 Timestamp [UCT]: 2025-01-24 15:36:59 Age [y:d:h:m:s]: 00:331:14:45:09
Block: 1204372 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234586 RingCT/type: yes/0
Extra: 01f438add11e4d27128c4b91986e13aba657f303c34ef2a7990290758d2c8d8d240211000000191f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fb63e2fe4b7a34e0e0d4a6f9d5d3f4a028ad1231232b32f035fcd69ed30d4a32 0.600000000000 1691057 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": 1204382, "vin": [ { "gen": { "height": 1204372 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb63e2fe4b7a34e0e0d4a6f9d5d3f4a028ad1231232b32f035fcd69ed30d4a32" } } ], "extra": [ 1, 244, 56, 173, 209, 30, 77, 39, 18, 140, 75, 145, 152, 110, 19, 171, 166, 87, 243, 3, 195, 78, 242, 167, 153, 2, 144, 117, 141, 44, 141, 141, 36, 2, 17, 0, 0, 0, 25, 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