Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6233a484de583e9a266c2a348fe24ba582dc008ac2f7507a1d56e64c148ed1f2

Tx prefix hash: 9b832ae0d4192403da76eab0841d44ac1fb1e9a15ed364b1ae4cba76a3c1d8ca
Tx public key: bf029141b75d56dde5045ae249000f5fa58ccf41007e3dcf79405d7a6971d792
Timestamp: 1656790522 Timestamp [UCT]: 2022-07-02 19:35:22 Age [y:d:h:m:s]: 02:258:15:41:37
Block: 535250 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 705991 RingCT/type: yes/0
Extra: 01bf029141b75d56dde5045ae249000f5fa58ccf41007e3dcf79405d7a6971d7920211000000084da16a3a000000000000000000

1 output(s) for total of 10.339385093000 dcy

stealth address amount amount idx
00: 73432fc3560aef83f75d24ea27d120c6afab13148d5c99d98f58b6aac994c1e5 10.339385093000 964865 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": 535260, "vin": [ { "gen": { "height": 535250 } } ], "vout": [ { "amount": 10339385093, "target": { "key": "73432fc3560aef83f75d24ea27d120c6afab13148d5c99d98f58b6aac994c1e5" } } ], "extra": [ 1, 191, 2, 145, 65, 183, 93, 86, 221, 229, 4, 90, 226, 73, 0, 15, 95, 165, 140, 207, 65, 0, 126, 61, 207, 121, 64, 93, 122, 105, 113, 215, 146, 2, 17, 0, 0, 0, 8, 77, 161, 106, 58, 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