Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7a11289957c5ab929630a2ad920b4885fb01e45a25748a9ededfecff319a5f9

Tx prefix hash: 675a31e34c9151aa5144d1cb79447aab2a1716c793ee3951bd1ffd2510e94e9b
Tx public key: 664bdeba3b77e0939b99ccebfc19142d4c659c610cbb7e7875b7e13710349124
Timestamp: 1580725538 Timestamp [UCT]: 2020-02-03 10:25:38 Age [y:d:h:m:s]: 05:039:02:09:40
Block: 57871 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1179817 RingCT/type: yes/0
Extra: 01664bdeba3b77e0939b99ccebfc19142d4c659c610cbb7e7875b7e137103491240211000000054ac5aa02000000000000000000

1 output(s) for total of 394.691414408000 dcy

stealth address amount amount idx
00: a646cc0c63547e23e719fb4ea3f7bd567c84712952d4e95250d139d218a3f5d4 394.691414408000 107004 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": 57881, "vin": [ { "gen": { "height": 57871 } } ], "vout": [ { "amount": 394691414408, "target": { "key": "a646cc0c63547e23e719fb4ea3f7bd567c84712952d4e95250d139d218a3f5d4" } } ], "extra": [ 1, 102, 75, 222, 186, 59, 119, 224, 147, 155, 153, 204, 235, 252, 25, 20, 45, 76, 101, 156, 97, 12, 187, 126, 120, 117, 183, 225, 55, 16, 52, 145, 36, 2, 17, 0, 0, 0, 5, 74, 197, 170, 2, 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