Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2c416d0c728a6978efbfbe08be773c1f2407046c07484d57feba579143d6a64

Tx prefix hash: b8ebb6252c1e556ccbf50789e475796ed4d238591af26638111fced481cf7ac4
Tx public key: 08dcfd94ea88d8ba5e4f69a26a07175eab93d4ca83ab39685221f7e291a2c170
Timestamp: 1577823032 Timestamp [UCT]: 2019-12-31 20:10:32 Age [y:d:h:m:s]: 04:334:06:39:56
Block: 35988 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1127987 RingCT/type: yes/0
Extra: 0108dcfd94ea88d8ba5e4f69a26a07175eab93d4ca83ab39685221f7e291a2c1700211000000244ac5aa02000000000000000000

1 output(s) for total of 466.452104001000 dcy

stealth address amount amount idx
00: f04dbc7f290494c37abe89d4a34fa54cfbbf86220d9ec4788f2a4ac8e267d1e9 466.452104001000 60796 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": 35998, "vin": [ { "gen": { "height": 35988 } } ], "vout": [ { "amount": 466452104001, "target": { "key": "f04dbc7f290494c37abe89d4a34fa54cfbbf86220d9ec4788f2a4ac8e267d1e9" } } ], "extra": [ 1, 8, 220, 253, 148, 234, 136, 216, 186, 94, 79, 105, 162, 106, 7, 23, 94, 171, 147, 212, 202, 131, 171, 57, 104, 82, 33, 247, 226, 145, 162, 193, 112, 2, 17, 0, 0, 0, 36, 74, 197, 170, 2, 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