Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03efa42ff2f40d2c987ede44e489f88a9a2629f3e224bee443a8b368d15847ac

Tx prefix hash: 8e62a78f51df8351343bf8b0fb22c7040aa0821ca48f0a1e0ce2e55d20dccf0c
Tx public key: ce9dc3e5162350ba85f84f23ce47bb2d90c5952658720f99ce152e2d67f7a39b
Timestamp: 1658358837 Timestamp [UCT]: 2022-07-20 23:13:57 Age [y:d:h:m:s]: 02:208:06:49:44
Block: 548163 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 670013 RingCT/type: yes/0
Extra: 01ce9dc3e5162350ba85f84f23ce47bb2d90c5952658720f99ce152e2d67f7a39b021100000018d3fcec30000000000000000000

1 output(s) for total of 9.369330583000 dcy

stealth address amount amount idx
00: 2b9f54fd97e985ab029a5e704073b4e312c277e4671bac485f40bff809661abd 9.369330583000 979388 of 0

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": 548173, "vin": [ { "gen": { "height": 548163 } } ], "vout": [ { "amount": 9369330583, "target": { "key": "2b9f54fd97e985ab029a5e704073b4e312c277e4671bac485f40bff809661abd" } } ], "extra": [ 1, 206, 157, 195, 229, 22, 35, 80, 186, 133, 248, 79, 35, 206, 71, 187, 45, 144, 197, 149, 38, 88, 114, 15, 153, 206, 21, 46, 45, 103, 247, 163, 155, 2, 17, 0, 0, 0, 24, 211, 252, 236, 48, 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