Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fdcb7d9da75ff09d2484abef6cab99a1fd161202385c2c525aa5d2202fdcccb8

Tx prefix hash: f843b69f19dce1cf827b9f8f203d382bc959ed57386abca42732a666e1edf5de
Tx public key: 973bcf28430ed186bcfd3971cbbd0e09e3535af30ee5ce63ecf3877e36faac36
Timestamp: 1582078797 Timestamp [UCT]: 2020-02-19 02:19:57 Age [y:d:h:m:s]: 05:260:03:09:01
Block: 67793 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1336783 RingCT/type: yes/0
Extra: 01973bcf28430ed186bcfd3971cbbd0e09e3535af30ee5ce63ecf3877e36faac360211000000034943cd9f000000000000000000

1 output(s) for total of 365.910149267000 dcy

stealth address amount amount idx
00: 094cd3e5f345cb889013929c1e28459aa335b34a5e364cef67368479ccf6cea2 365.910149267000 124905 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": 67803, "vin": [ { "gen": { "height": 67793 } } ], "vout": [ { "amount": 365910149267, "target": { "key": "094cd3e5f345cb889013929c1e28459aa335b34a5e364cef67368479ccf6cea2" } } ], "extra": [ 1, 151, 59, 207, 40, 67, 14, 209, 134, 188, 253, 57, 113, 203, 189, 14, 9, 227, 83, 90, 243, 14, 229, 206, 99, 236, 243, 135, 126, 54, 250, 172, 54, 2, 17, 0, 0, 0, 3, 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