Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce316ce6e41c0df984fe11624b8807d65fd412a97f65d65bdcb1864c3733c5de

Tx prefix hash: 6769de5640f51e94051f7e81bad2a3b5ee07ecdcc3233c37fa000947fcde8448
Tx public key: 1b5a3758a02eaa32100c89222330d9569d8fd9c7f94a7b48c8b4ade6fb3fd66c
Timestamp: 1582050961 Timestamp [UCT]: 2020-02-18 18:36:01 Age [y:d:h:m:s]: 05:087:09:20:48
Block: 67691 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1215506 RingCT/type: yes/0
Extra: 011b5a3758a02eaa32100c89222330d9569d8fd9c7f94a7b48c8b4ade6fb3fd66c0211000000064943cd9f000000000000000000

1 output(s) for total of 366.209671814000 dcy

stealth address amount amount idx
00: 1ef8c1281895bec034b4885494d6dab85b62954b7c28afb9ce8ea1527785a46a 366.209671814000 124666 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": 67701, "vin": [ { "gen": { "height": 67691 } } ], "vout": [ { "amount": 366209671814, "target": { "key": "1ef8c1281895bec034b4885494d6dab85b62954b7c28afb9ce8ea1527785a46a" } } ], "extra": [ 1, 27, 90, 55, 88, 160, 46, 170, 50, 16, 12, 137, 34, 35, 48, 217, 86, 157, 143, 217, 199, 249, 74, 123, 72, 200, 180, 173, 230, 251, 63, 214, 108, 2, 17, 0, 0, 0, 6, 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