Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5b71f34d2765e0ea484cdc833b0d14151a2cb471f6d6204507f6cf2b087f976

Tx prefix hash: 7884d2606955785571d06e5a0ebbde3f2c1367fe689d4b75d7b41f5c0bc2f3fa
Tx public key: cdfbfdd0decbdfcdf86971d8b2775d1ee3247c49b58ff885cb5ff6dd07f695c6
Timestamp: 1726068420 Timestamp [UCT]: 2024-09-11 15:27:00 Age [y:d:h:m:s]: 00:119:13:51:33
Block: 1107863 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85520 RingCT/type: yes/0
Extra: 01cdfbfdd0decbdfcdf86971d8b2775d1ee3247c49b58ff885cb5ff6dd07f695c602110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1c28b58308672c75cec4fa74db44df639a9f3ff79f24fe538400f4b3a3c303f 0.600000000000 1585558 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": 1107873, "vin": [ { "gen": { "height": 1107863 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1c28b58308672c75cec4fa74db44df639a9f3ff79f24fe538400f4b3a3c303f" } } ], "extra": [ 1, 205, 251, 253, 208, 222, 203, 223, 205, 248, 105, 113, 216, 178, 119, 93, 30, 227, 36, 124, 73, 181, 143, 248, 133, 203, 95, 246, 221, 7, 246, 149, 198, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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