Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0042869e105d2d14e9a52a17029dcf864dbe1320656e0620c3f6c7302e40303

Tx prefix hash: 7ef5810153d36dc033a09d4ca1d519dfafdc9a9028762a470f091336b133c299
Tx public key: 5fb43c79f2665aeb5d6f9eb1f36458c12071513bf30932a33042257e98e73406
Timestamp: 1711794748 Timestamp [UCT]: 2024-03-30 10:32:28 Age [y:d:h:m:s]: 01:223:14:26:40
Block: 989558 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 418461 RingCT/type: yes/0
Extra: 015fb43c79f2665aeb5d6f9eb1f36458c12071513bf30932a33042257e98e7340602110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38b99c5034a5de7a429e7db92d804741dadff0617b4f02da0ad2ba41ac1383c9 0.600000000000 1449857 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": 989568, "vin": [ { "gen": { "height": 989558 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38b99c5034a5de7a429e7db92d804741dadff0617b4f02da0ad2ba41ac1383c9" } } ], "extra": [ 1, 95, 180, 60, 121, 242, 102, 90, 235, 93, 111, 158, 177, 243, 100, 88, 193, 32, 113, 81, 59, 243, 9, 50, 163, 48, 66, 37, 126, 152, 231, 52, 6, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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