Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2cfc4bab0613dbf22e18b6fbfb391283e1a6b21bb1cec648be4050c25884bac0

Tx prefix hash: ca69a9ba731b345c92aeb590aa1ae9ade687c97552e03e5ed69047b1215fb868
Tx public key: a7198e3f939d47f93c07ddb10e8504add842d94ee30f4f8a32b3e461a7acc8c8
Timestamp: 1722099738 Timestamp [UCT]: 2024-07-27 17:02:18 Age [y:d:h:m:s]: 00:183:06:00:25
Block: 1074963 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130948 RingCT/type: yes/0
Extra: 01a7198e3f939d47f93c07ddb10e8504add842d94ee30f4f8a32b3e461a7acc8c802110000000ce914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e726604fe67e4336cda36a48cabc36ff78f5d166024d5ae2514a9a345858d06 0.600000000000 1547482 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": 1074973, "vin": [ { "gen": { "height": 1074963 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e726604fe67e4336cda36a48cabc36ff78f5d166024d5ae2514a9a345858d06" } } ], "extra": [ 1, 167, 25, 142, 63, 147, 157, 71, 249, 60, 7, 221, 177, 14, 133, 4, 173, 216, 66, 217, 78, 227, 15, 79, 138, 50, 179, 228, 97, 167, 172, 200, 200, 2, 17, 0, 0, 0, 12, 233, 20, 221, 21, 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