Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f88d79c39aa5b70b872131ce2e4a2e777d71c08d59580bf30064065843b683df

Tx prefix hash: b650462d911d76631e1eea541f0fbfd3d96edf6a6c4d6ebf08e4f4ff50e35e60
Tx public key: fc200ec2d5d7329e643e80875b37fc0f3989f11de6ac8e45bc051d23f0923f99
Timestamp: 1737345070 Timestamp [UCT]: 2025-01-20 03:51:10 Age [y:d:h:m:s]: 00:149:08:40:44
Block: 1201164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106493 RingCT/type: yes/0
Extra: 01fc200ec2d5d7329e643e80875b37fc0f3989f11de6ac8e45bc051d23f0923f990211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8fc3fec28492ee2f440b6a13429fd7e419b8f99465cdc5024e3136fda454a175 0.600000000000 1687813 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": 1201174, "vin": [ { "gen": { "height": 1201164 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8fc3fec28492ee2f440b6a13429fd7e419b8f99465cdc5024e3136fda454a175" } } ], "extra": [ 1, 252, 32, 14, 194, 213, 215, 50, 158, 100, 62, 128, 135, 91, 55, 252, 15, 57, 137, 241, 29, 230, 172, 142, 69, 188, 5, 29, 35, 240, 146, 63, 153, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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