Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae71c9c75ba0273c9a87c1771a361f82d1d535aaf86b008d83fd2d30460147a8

Tx prefix hash: 88451283cdb160e2c2cea3735449d1c6ac52ba29f86fa03b105bbe09bf3be3c7
Tx public key: bb77df516f5ab836378d18e191c7a6e0f2d1e980ac25d3059c694c9d9d4ca661
Timestamp: 1702987225 Timestamp [UCT]: 2023-12-19 12:00:25 Age [y:d:h:m:s]: 01:127:23:43:37
Block: 916512 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 352617 RingCT/type: yes/0
Extra: 01bb77df516f5ab836378d18e191c7a6e0f2d1e980ac25d3059c694c9d9d4ca66102110000000433af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ab52c7da8eb205eb95da74a229f08cc9039142e8ae9221e36ce9751dadfe5f9 0.600000000000 1374064 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": 916522, "vin": [ { "gen": { "height": 916512 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ab52c7da8eb205eb95da74a229f08cc9039142e8ae9221e36ce9751dadfe5f9" } } ], "extra": [ 1, 187, 119, 223, 81, 111, 90, 184, 54, 55, 141, 24, 225, 145, 199, 166, 224, 242, 209, 233, 128, 172, 37, 211, 5, 156, 105, 76, 157, 157, 76, 166, 97, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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