Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5700f16ab2a9e6ea3c2eb03d89e5160824454af594fc68ff96eee1ed0b489a3

Tx prefix hash: d36ff034d13d6a4a5401da63925664012a5ae5435f1a12bcf4eb19d32b5356d8
Tx public key: 1c6dab0785997d584a61f8b49eadb3439a1520a3ca01ff1819f96ef86d58c6e6
Timestamp: 1680710541 Timestamp [UCT]: 2023-04-05 16:02:21 Age [y:d:h:m:s]: 02:038:17:20:50
Block: 732486 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 549448 RingCT/type: yes/0
Extra: 011c6dab0785997d584a61f8b49eadb3439a1520a3ca01ff1819f96ef86d58c6e60211000000075029cbac000000000000000000

1 output(s) for total of 2.295990260000 dcy

stealth address amount amount idx
00: a40a9ff199e66d30d29d89a58fd7c2750328eb3b72efb796f3985a187a51ab7c 2.295990260000 1178427 of 0

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": 732496, "vin": [ { "gen": { "height": 732486 } } ], "vout": [ { "amount": 2295990260, "target": { "key": "a40a9ff199e66d30d29d89a58fd7c2750328eb3b72efb796f3985a187a51ab7c" } } ], "extra": [ 1, 28, 109, 171, 7, 133, 153, 125, 88, 74, 97, 248, 180, 158, 173, 179, 67, 154, 21, 32, 163, 202, 1, 255, 24, 25, 249, 110, 248, 109, 88, 198, 230, 2, 17, 0, 0, 0, 7, 80, 41, 203, 172, 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