Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb067a4797464a2185a8cd47a08402a0ba10821ac89696e36bf99c53c2157214

Tx prefix hash: ca4ffd634db47ec5f2a8806a5bb38c8770bc5b186b4cbc71e679ee1ba2907222
Tx public key: 286e6ad0c51169e5c441483704b4b347177721d6f787002560e0d7a7f505dac8
Timestamp: 1648878472 Timestamp [UCT]: 2022-04-02 05:47:52 Age [y:d:h:m:s]: 02:312:05:49:34
Block: 471423 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 742629 RingCT/type: yes/0
Extra: 01286e6ad0c51169e5c441483704b4b347177721d6f787002560e0d7a7f505dac80211000000012e6b1fd5000000000000000000

1 output(s) for total of 16.825971594000 dcy

stealth address amount amount idx
00: 8e0e9bb1d4b11c66d23eb55bc741155b17e7987c262487f78a266afbce06e763 16.825971594000 890767 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": 471433, "vin": [ { "gen": { "height": 471423 } } ], "vout": [ { "amount": 16825971594, "target": { "key": "8e0e9bb1d4b11c66d23eb55bc741155b17e7987c262487f78a266afbce06e763" } } ], "extra": [ 1, 40, 110, 106, 208, 197, 17, 105, 229, 196, 65, 72, 55, 4, 180, 179, 71, 23, 119, 33, 214, 247, 135, 0, 37, 96, 224, 215, 167, 245, 5, 218, 200, 2, 17, 0, 0, 0, 1, 46, 107, 31, 213, 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