Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c29cf11fee93ee40c2cd02c87c765ca3fa5ea7add73a115a70c9499092a60e98

Tx prefix hash: 95a92515362ca7276a3377f91071aa2fa39311630c6d36079fb87e128e231db3
Tx public key: cda31a0e769f6c7a0d2c3285ae9d8a529637a267fac29b8dafd90997f3844fec
Timestamp: 1577392708 Timestamp [UCT]: 2019-12-26 20:38:28 Age [y:d:h:m:s]: 04:335:20:18:27
Block: 32441 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1129089 RingCT/type: yes/0
Extra: 01cda31a0e769f6c7a0d2c3285ae9d8a529637a267fac29b8dafd90997f3844fec0211000000114943cd9f000000000000000000

1 output(s) for total of 479.192882499000 dcy

stealth address amount amount idx
00: 03ec4f175a892c9689f844b82ed87dba0457403ae03a61990648dabab476348a 479.192882499000 53948 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": 32451, "vin": [ { "gen": { "height": 32441 } } ], "vout": [ { "amount": 479192882499, "target": { "key": "03ec4f175a892c9689f844b82ed87dba0457403ae03a61990648dabab476348a" } } ], "extra": [ 1, 205, 163, 26, 14, 118, 159, 108, 122, 13, 44, 50, 133, 174, 157, 138, 82, 150, 55, 162, 103, 250, 194, 155, 141, 175, 217, 9, 151, 243, 132, 79, 236, 2, 17, 0, 0, 0, 17, 73, 67, 205, 159, 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