Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 935e56123c96cf5ef1bc1ccc02fb38b4364b4fb64d6472dbf27dbeedc4cbf8b3

Tx prefix hash: f7c661e4ba041af99d4dc704a0af5385d3d068e13758196857954bba1602b342
Tx public key: 8fb04d5ce039dc15cfadba1aee1360d3ca298ec1d5090011cea5002b21b26832
Timestamp: 1661221956 Timestamp [UCT]: 2022-08-23 02:32:36 Age [y:d:h:m:s]: 03:076:14:04:55
Block: 571787 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 834538 RingCT/type: yes/0
Extra: 018fb04d5ce039dc15cfadba1aee1360d3ca298ec1d5090011cea5002b21b26832021100000001e6d27f9c000000000000000000

1 output(s) for total of 7.824064270000 dcy

stealth address amount amount idx
00: db59ee8b1e832f156683a87cf3c2a2d73eb7737b28cf4c1aaa2728e2c3798c4f 7.824064270000 1005011 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": 571797, "vin": [ { "gen": { "height": 571787 } } ], "vout": [ { "amount": 7824064270, "target": { "key": "db59ee8b1e832f156683a87cf3c2a2d73eb7737b28cf4c1aaa2728e2c3798c4f" } } ], "extra": [ 1, 143, 176, 77, 92, 224, 57, 220, 21, 207, 173, 186, 26, 238, 19, 96, 211, 202, 41, 142, 193, 213, 9, 0, 17, 206, 165, 0, 43, 33, 178, 104, 50, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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