Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c18b44d9351b0722ac7107e8632f5f7a04f7f764e4a7009920e00f7d72a99f57

Tx prefix hash: 64cdcff4e7bca3de2a2486f554941d0584d64ca0c3192a139bb7894fb738cbca
Tx public key: d5357cacc83db0f26095929d55ddee053d89ee89d1a77ba530b5e5fef68f896c
Timestamp: 1703939651 Timestamp [UCT]: 2023-12-30 12:34:11 Age [y:d:h:m:s]: 01:320:07:13:01
Block: 924410 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 487754 RingCT/type: yes/0
Extra: 01d5357cacc83db0f26095929d55ddee053d89ee89d1a77ba530b5e5fef68f896c0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fe1678b440f1f94a896d33b0c18abfb87fd1082c4260e1390624020d1ab36fea 0.600000000000 1382158 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": 924420, "vin": [ { "gen": { "height": 924410 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe1678b440f1f94a896d33b0c18abfb87fd1082c4260e1390624020d1ab36fea" } } ], "extra": [ 1, 213, 53, 124, 172, 200, 61, 176, 242, 96, 149, 146, 157, 85, 221, 238, 5, 61, 137, 238, 137, 209, 167, 123, 165, 48, 181, 229, 254, 246, 143, 137, 108, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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