Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07d517a9a9372f34aeeb0f13e8ae3441407ae5b34c9a0f2eb043fa1c1e95154c

Tx prefix hash: 6fa5241a5924ff8f7dc3cdc8a71b7e98ce4026f433f3786cd0d33fe9aac898d0
Tx public key: 6432a49d57505a80056fc9cd9f2159bf949a415a903938092dbc33a25d499a3b
Timestamp: 1720451572 Timestamp [UCT]: 2024-07-08 15:12:52 Age [y:d:h:m:s]: 00:139:09:40:41
Block: 1061310 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99745 RingCT/type: yes/0
Extra: 016432a49d57505a80056fc9cd9f2159bf949a415a903938092dbc33a25d499a3b02110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 63f857d6aa21c7cfd78e0188c0512c0510f265d17002285461205a5f799e52b1 0.600000000000 1531801 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": 1061320, "vin": [ { "gen": { "height": 1061310 } } ], "vout": [ { "amount": 600000000, "target": { "key": "63f857d6aa21c7cfd78e0188c0512c0510f265d17002285461205a5f799e52b1" } } ], "extra": [ 1, 100, 50, 164, 157, 87, 80, 90, 128, 5, 111, 201, 205, 159, 33, 89, 191, 148, 154, 65, 90, 144, 57, 56, 9, 45, 188, 51, 162, 93, 73, 154, 59, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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