Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b438d864d3c6bd080f306860687c837b91c745e9a42d2e3e919ee36ac7ca5ad8

Tx prefix hash: bbaae46b996e46de12b78101e5d8838d1384ba6ae8a324762c6e6f97e588cf49
Tx public key: 5c6fa7482f099a3450c7e6fd066bf7542337c578adb0a845991716ce72451254
Timestamp: 1724547688 Timestamp [UCT]: 2024-08-25 01:01:28 Age [y:d:h:m:s]: 00:138:17:18:16
Block: 1095286 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99197 RingCT/type: yes/0
Extra: 015c6fa7482f099a3450c7e6fd066bf7542337c578adb0a845991716ce72451254021100000002e337358e000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e408d1c39c1453359ab474827491e431e036e0eefb0c09aa02a6d8ef6b2e6242 0.600000000000 1570445 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": 1095296, "vin": [ { "gen": { "height": 1095286 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e408d1c39c1453359ab474827491e431e036e0eefb0c09aa02a6d8ef6b2e6242" } } ], "extra": [ 1, 92, 111, 167, 72, 47, 9, 154, 52, 80, 199, 230, 253, 6, 107, 247, 84, 35, 55, 197, 120, 173, 176, 168, 69, 153, 23, 22, 206, 114, 69, 18, 84, 2, 17, 0, 0, 0, 2, 227, 55, 53, 142, 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