Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c13898f7a240296d67f22213820ebc1993ee8906252159a107602a1b40d7d91

Tx prefix hash: abec6b9de6ed6c04513fd8d58a3aeef0754507b376c770309dc9fb99ea0e61fb
Tx public key: 6a011a73ec8ca19394a00152059c022bb0ad8c7b6de96146d9d81a232954d530
Timestamp: 1718606854 Timestamp [UCT]: 2024-06-17 06:47:34 Age [y:d:h:m:s]: 00:284:16:26:14
Block: 1046009 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203425 RingCT/type: yes/0
Extra: 016a011a73ec8ca19394a00152059c022bb0ad8c7b6de96146d9d81a232954d53002110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee2e8b7a3a440a0a3be0c7d8292ed907062a16e2b856cd3d88f7a8985fe9711b 0.600000000000 1515748 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": 1046019, "vin": [ { "gen": { "height": 1046009 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee2e8b7a3a440a0a3be0c7d8292ed907062a16e2b856cd3d88f7a8985fe9711b" } } ], "extra": [ 1, 106, 1, 26, 115, 236, 140, 161, 147, 148, 160, 1, 82, 5, 156, 2, 43, 176, 173, 140, 123, 109, 233, 97, 70, 217, 216, 26, 35, 41, 84, 213, 48, 2, 17, 0, 0, 0, 2, 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