Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ee4e595b08be653d6753ce2d225e01d6c6e99c955924ae128e62f74d655d33a

Tx prefix hash: fefcc3cadbe44538c64d8262c04be73a21dffff8d5d236a5d7d88b93eb230cd0
Tx public key: 9d7c0668deaca416d3019b1f5561fbeb3384bb7b549ade4ceb6daf6bb5cc7fa5
Timestamp: 1726128772 Timestamp [UCT]: 2024-09-12 08:12:52 Age [y:d:h:m:s]: 00:232:04:13:05
Block: 1108358 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165792 RingCT/type: yes/0
Extra: 019d7c0668deaca416d3019b1f5561fbeb3384bb7b549ade4ceb6daf6bb5cc7fa502110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 566f2381c359d13d94b6e156e1f9ade8725b8f61c16e4e47827d7d1639eb38c9 0.600000000000 1586225 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": 1108368, "vin": [ { "gen": { "height": 1108358 } } ], "vout": [ { "amount": 600000000, "target": { "key": "566f2381c359d13d94b6e156e1f9ade8725b8f61c16e4e47827d7d1639eb38c9" } } ], "extra": [ 1, 157, 124, 6, 104, 222, 172, 164, 22, 211, 1, 155, 31, 85, 97, 251, 235, 51, 132, 187, 123, 84, 154, 222, 76, 235, 109, 175, 107, 181, 204, 127, 165, 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