Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 876203fac006d743ceb0b9c8478bec4e17364d4f9e87e9e9e1c9515fd2ec9936

Tx prefix hash: fb90646384931edb22be38a40963e8c7483eda60d30e565a1d1a782f80762513
Tx public key: a66ccdf4d8d955b64fa96bf502016e1cb57d4ce29a29e5bc70644df4ba5aa6e7
Timestamp: 1685543839 Timestamp [UCT]: 2023-05-31 14:37:19 Age [y:d:h:m:s]: 02:012:23:51:18
Block: 772151 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 531357 RingCT/type: yes/0
Extra: 01a66ccdf4d8d955b64fa96bf502016e1cb57d4ce29a29e5bc70644df4ba5aa6e7021100000006faf35c9c000000000000000000

1 output(s) for total of 1.696459017000 dcy

stealth address amount amount idx
00: 52d37982de04963bdda7804ec33c351494d9888163a4e808bc5cc2e4e8192f21 1.696459017000 1221544 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": 772161, "vin": [ { "gen": { "height": 772151 } } ], "vout": [ { "amount": 1696459017, "target": { "key": "52d37982de04963bdda7804ec33c351494d9888163a4e808bc5cc2e4e8192f21" } } ], "extra": [ 1, 166, 108, 205, 244, 216, 217, 85, 182, 79, 169, 107, 245, 2, 1, 110, 28, 181, 125, 76, 226, 154, 41, 229, 188, 112, 100, 77, 244, 186, 90, 166, 231, 2, 17, 0, 0, 0, 6, 250, 243, 92, 156, 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