Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9de1c05e20fa5d67a7ec21400326da8263573648cc7576e8d3e56482319e3d40

Tx prefix hash: a47cfebc8bbb393c0346151508d06caef9c1384f48c17b7f4f9a60ef3c585696
Tx public key: c7b3e826a170933af3fcd36ebe78ecf802f5b37a25975a0662cabd644a1c2d30
Timestamp: 1716538852 Timestamp [UCT]: 2024-05-24 08:20:52 Age [y:d:h:m:s]: 00:243:11:04:05
Block: 1028873 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174181 RingCT/type: yes/0
Extra: 01c7b3e826a170933af3fcd36ebe78ecf802f5b37a25975a0662cabd644a1c2d3002110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a66610d34a20bb3421a995eea804747e8f7c7ab9f3b65f53e03c48629bdcfe6 0.600000000000 1496872 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": 1028883, "vin": [ { "gen": { "height": 1028873 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a66610d34a20bb3421a995eea804747e8f7c7ab9f3b65f53e03c48629bdcfe6" } } ], "extra": [ 1, 199, 179, 232, 38, 161, 112, 147, 58, 243, 252, 211, 110, 190, 120, 236, 248, 2, 245, 179, 122, 37, 151, 90, 6, 98, 202, 189, 100, 74, 28, 45, 48, 2, 17, 0, 0, 0, 3, 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