Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a9b5e49f8385d5751c05b1e047b75b67c9ccd5929af379ed0050dfa51b8b964

Tx prefix hash: 4723e1baf7eb153271c2f718c30d5afd20001ec62933db9f87a2ab3b46d31b7c
Tx public key: a915fffea297ccccbbf02584c8e0948cb7f18382a772abf08c92776e43926a8c
Timestamp: 1577619230 Timestamp [UCT]: 2019-12-29 11:33:50 Age [y:d:h:m:s]: 05:134:23:04:33
Block: 34323 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1246213 RingCT/type: yes/0
Extra: 01a915fffea297ccccbbf02584c8e0948cb7f18382a772abf08c92776e43926a8c02110000001dac34bf9e000000000000000000

1 output(s) for total of 472.361517126000 dcy

stealth address amount amount idx
00: c47c89f4d5b877cec4ad103b2d4553831206f27d19d5bc8e76e7beaa060849a1 472.361517126000 57730 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": 34333, "vin": [ { "gen": { "height": 34323 } } ], "vout": [ { "amount": 472361517126, "target": { "key": "c47c89f4d5b877cec4ad103b2d4553831206f27d19d5bc8e76e7beaa060849a1" } } ], "extra": [ 1, 169, 21, 255, 254, 162, 151, 204, 204, 187, 240, 37, 132, 200, 224, 148, 140, 183, 241, 131, 130, 167, 114, 171, 240, 140, 146, 119, 110, 67, 146, 106, 140, 2, 17, 0, 0, 0, 29, 172, 52, 191, 158, 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