Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0817f78ad9e03753c7c00b056d07947a1a4039ea5cdba097914c307a301d6688

Tx prefix hash: fe922b66a36ea2f75d546d61e615a417dedfcabf94629817c989effab87a017a
Tx public key: d870c66ff399a3a4743f8548ffc70dbc9178f1a2854ca658a972d4f4c69dbfef
Timestamp: 1727774276 Timestamp [UCT]: 2024-10-01 09:17:56 Age [y:d:h:m:s]: 00:082:15:58:38
Block: 1122016 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59123 RingCT/type: yes/0
Extra: 01d870c66ff399a3a4743f8548ffc70dbc9178f1a2854ca658a972d4f4c69dbfef021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f685b1f4fd4c8ac35fb0a8851738d98ce702ef89dfaf7e161d9881e0b57a654 0.600000000000 1604381 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": 1122026, "vin": [ { "gen": { "height": 1122016 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f685b1f4fd4c8ac35fb0a8851738d98ce702ef89dfaf7e161d9881e0b57a654" } } ], "extra": [ 1, 216, 112, 198, 111, 243, 153, 163, 164, 116, 63, 133, 72, 255, 199, 13, 188, 145, 120, 241, 162, 133, 76, 166, 88, 169, 114, 212, 244, 198, 157, 191, 239, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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