Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f26d9922b66697dbe7436aa2b3c1757ff23c93b2d1d7e9f682e86820c8cb63d

Tx prefix hash: 26e5f5bcb213e9de1c9f9afe038ff2db9edb0b389656ef591c4313e8dad03380
Tx public key: 2c48b661769cd8de76156a22f86951fd646ca4637eb220e727d99c1e68044cce
Timestamp: 1707962466 Timestamp [UCT]: 2024-02-15 02:01:06 Age [y:d:h:m:s]: 01:050:18:37:15
Block: 957750 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297330 RingCT/type: yes/0
Extra: 012c48b661769cd8de76156a22f86951fd646ca4637eb220e727d99c1e68044cce02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f364ac5d5b5bb3c7b329cc2c795a354ba9b5a5bce90970f3790fd994fb18e186 0.600000000000 1417099 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": 957760, "vin": [ { "gen": { "height": 957750 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f364ac5d5b5bb3c7b329cc2c795a354ba9b5a5bce90970f3790fd994fb18e186" } } ], "extra": [ 1, 44, 72, 182, 97, 118, 156, 216, 222, 118, 21, 106, 34, 248, 105, 81, 253, 100, 108, 164, 99, 126, 178, 32, 231, 39, 217, 156, 30, 104, 4, 76, 206, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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