Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14716b1e4cda9b2eedf9e2140d860df04abbffa67640b2965b7d5419817b598c

Tx prefix hash: 4dc635193a1483abea8106b86d27319c59785969d73ffdfe4fd3daa638d77f02
Tx public key: b71a52ca028f0cb8e2ddd5d980b208ae9fc27a61bfb3689aae05cd4900e0e5e8
Timestamp: 1580616350 Timestamp [UCT]: 2020-02-02 04:05:50 Age [y:d:h:m:s]: 05:104:13:17:56
Block: 56841 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1226755 RingCT/type: yes/0
Extra: 01b71a52ca028f0cb8e2ddd5d980b208ae9fc27a61bfb3689aae05cd4900e0e5e8021100000001391a8d0e000000000000000000

1 output(s) for total of 397.805235320000 dcy

stealth address amount amount idx
00: d74bb1abc7d53e0fc2a8d63be3a4b3b48ed63c4d762a3bc72a9395b62c34336a 397.805235320000 104818 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": 56851, "vin": [ { "gen": { "height": 56841 } } ], "vout": [ { "amount": 397805235320, "target": { "key": "d74bb1abc7d53e0fc2a8d63be3a4b3b48ed63c4d762a3bc72a9395b62c34336a" } } ], "extra": [ 1, 183, 26, 82, 202, 2, 143, 12, 184, 226, 221, 213, 217, 128, 178, 8, 174, 159, 194, 122, 97, 191, 179, 104, 154, 174, 5, 205, 73, 0, 224, 229, 232, 2, 17, 0, 0, 0, 1, 57, 26, 141, 14, 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