Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a66eb182bafad85fe5dcfb50935b8f3fffcab754ce656de86e26126fd9f78874

Tx prefix hash: 7fcef8f48201b36688e79af012cec95983a0aef396e6f21566b75b34fb117291
Tx public key: 5812b3a9360006ccf8415a8217ed4dc033350ca3c24f6a306d0b1ba79b5aa70e
Timestamp: 1733258484 Timestamp [UCT]: 2024-12-03 20:41:24 Age [y:d:h:m:s]: 00:114:17:32:18
Block: 1167371 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81800 RingCT/type: yes/0
Extra: 015812b3a9360006ccf8415a8217ed4dc033350ca3c24f6a306d0b1ba79b5aa70e021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e33bc3f991d1cb5e0089bd41cc68c9e264242d6f0879d472c61537f80d9729cc 0.600000000000 1653066 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": 1167381, "vin": [ { "gen": { "height": 1167371 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e33bc3f991d1cb5e0089bd41cc68c9e264242d6f0879d472c61537f80d9729cc" } } ], "extra": [ 1, 88, 18, 179, 169, 54, 0, 6, 204, 248, 65, 90, 130, 23, 237, 77, 192, 51, 53, 12, 163, 194, 79, 106, 48, 109, 11, 27, 167, 155, 90, 167, 14, 2, 17, 0, 0, 0, 2, 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