Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3cb7cc391c35ab9ae81b37d2d9b64c25f72a3bda311548a39406fe723af35073

Tx prefix hash: ca1584724999bb98b3f467961f234a3aee37321fd0ade46111e381f6f6e33f55
Tx public key: 0ede692cbf3457639405d308485591a1f494a847f0cea8dbe21e8e741013d7d9
Timestamp: 1581146338 Timestamp [UCT]: 2020-02-08 07:18:58 Age [y:d:h:m:s]: 05:026:00:08:12
Block: 60826 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1170975 RingCT/type: yes/0
Extra: 010ede692cbf3457639405d308485591a1f494a847f0cea8dbe21e8e741013d7d902110000000e8a2ee0d9000000000000000000

1 output(s) for total of 385.886005737000 dcy

stealth address amount amount idx
00: 064e967f7ea09ea338878a2a737f187febfe4776029ee9e6fb62cca52fc034c3 385.886005737000 112061 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": 60836, "vin": [ { "gen": { "height": 60826 } } ], "vout": [ { "amount": 385886005737, "target": { "key": "064e967f7ea09ea338878a2a737f187febfe4776029ee9e6fb62cca52fc034c3" } } ], "extra": [ 1, 14, 222, 105, 44, 191, 52, 87, 99, 148, 5, 211, 8, 72, 85, 145, 161, 244, 148, 168, 71, 240, 206, 168, 219, 226, 30, 142, 116, 16, 19, 215, 217, 2, 17, 0, 0, 0, 14, 138, 46, 224, 217, 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