Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9455269519ef1b00b819588ed25cea75aa2d8468780f52807285d460f2c4e82c

Tx prefix hash: 7f6a4dfeb7ebd14430800988d5ae58286f0b603d858e7daa5b31681f52597910
Tx public key: ceca44f3162fd24e414765de37868f86d7f5ff8dec5d4c42f6e7d362d63a1341
Timestamp: 1700489747 Timestamp [UCT]: 2023-11-20 14:15:47 Age [y:d:h:m:s]: 01:158:06:39:15
Block: 895800 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 374314 RingCT/type: yes/0
Extra: 01ceca44f3162fd24e414765de37868f86d7f5ff8dec5d4c42f6e7d362d63a1341021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.660454229000 dcy

stealth address amount amount idx
00: f86f6d22ccc0eb88213f877ad2298da0cd73a640be8944b07a447501dd541164 0.660454229000 1352047 of 0

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": 895810, "vin": [ { "gen": { "height": 895800 } } ], "vout": [ { "amount": 660454229, "target": { "key": "f86f6d22ccc0eb88213f877ad2298da0cd73a640be8944b07a447501dd541164" } } ], "extra": [ 1, 206, 202, 68, 243, 22, 47, 210, 78, 65, 71, 101, 222, 55, 134, 143, 134, 215, 245, 255, 141, 236, 93, 76, 66, 246, 231, 211, 98, 214, 58, 19, 65, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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