Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06ad22d54110ab8cb83266431493806cfd0708b65f722a5cbfc7d89cb27c2e9e

Tx prefix hash: 42ba1822af3ce845f158640ea9390a06162fe955db680c6a22f94a3c07102ac4
Tx public key: 641ab9213ade88e74df2dcf2f72cd7fed9c8ce07c6eed82718d963045e2e198e
Timestamp: 1722532285 Timestamp [UCT]: 2024-08-01 17:11:25 Age [y:d:h:m:s]: 00:247:19:30:31
Block: 1078548 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177005 RingCT/type: yes/0
Extra: 01641ab9213ade88e74df2dcf2f72cd7fed9c8ce07c6eed82718d963045e2e198e021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 93445c73944d1913b8ffebf6d95b72fef8ae0b6ba11f1d5c8511d5a9fc2fded7 0.600000000000 1551133 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": 1078558, "vin": [ { "gen": { "height": 1078548 } } ], "vout": [ { "amount": 600000000, "target": { "key": "93445c73944d1913b8ffebf6d95b72fef8ae0b6ba11f1d5c8511d5a9fc2fded7" } } ], "extra": [ 1, 100, 26, 185, 33, 58, 222, 136, 231, 77, 242, 220, 242, 247, 44, 215, 254, 217, 200, 206, 7, 198, 238, 216, 39, 24, 217, 99, 4, 94, 46, 25, 142, 2, 17, 0, 0, 0, 8, 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