Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96d68a22cf14cbb6eb9183f87b4338f77c5e8af66ca90cf7a73eb2bd9b9b25ab

Tx prefix hash: 62bb43c4488c5f0ea4bc5decdc87c0bb451683f8056e9d3a62b3b91b9cb8cedc
Tx public key: 28383a008fadad01e4e866e7a8da0e4865b378c275db852cef0bc6f4b084bb32
Timestamp: 1709415332 Timestamp [UCT]: 2024-03-02 21:35:32 Age [y:d:h:m:s]: 01:055:14:11:08
Block: 969815 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300749 RingCT/type: yes/0
Extra: 0128383a008fadad01e4e866e7a8da0e4865b378c275db852cef0bc6f4b084bb320211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f7a1272cd9464adfe78689c31b38b761b66fb5158e49ad0a282ca2370241efab 0.600000000000 1429664 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": 969825, "vin": [ { "gen": { "height": 969815 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f7a1272cd9464adfe78689c31b38b761b66fb5158e49ad0a282ca2370241efab" } } ], "extra": [ 1, 40, 56, 58, 0, 143, 173, 173, 1, 228, 232, 102, 231, 168, 218, 14, 72, 101, 179, 120, 194, 117, 219, 133, 44, 239, 11, 198, 244, 176, 132, 187, 50, 2, 17, 0, 0, 0, 2, 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