Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c7893d130c88c3dc5fd9501dd734fdc9222b195a46fa71c28ab5018aeb0b53a

Tx prefix hash: cfc22ef45f94abcf0b765055a148c62b3f483d7785db9d7ae6b9e9d7b09d7823
Tx public key: eff485df8e9ce9497eb48a61bad443150ea5819ab0e7721d0f55a5e6d3199f7d
Timestamp: 1610033674 Timestamp [UCT]: 2021-01-07 15:34:34 Age [y:d:h:m:s]: 03:273:00:32:55
Block: 175857 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 949930 RingCT/type: yes/0
Extra: 01eff485df8e9ce9497eb48a61bad443150ea5819ab0e7721d0f55a5e6d3199f7d021100000673df1e48bb000000000000000000

1 output(s) for total of 160.440281201000 dcy

stealth address amount amount idx
00: f776348c28142284737de0e0f5b39c7ac835b94951480ecb524f229473901797 160.440281201000 336295 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": 175867, "vin": [ { "gen": { "height": 175857 } } ], "vout": [ { "amount": 160440281201, "target": { "key": "f776348c28142284737de0e0f5b39c7ac835b94951480ecb524f229473901797" } } ], "extra": [ 1, 239, 244, 133, 223, 142, 156, 233, 73, 126, 180, 138, 97, 186, 212, 67, 21, 14, 165, 129, 154, 176, 231, 114, 29, 15, 85, 165, 230, 211, 25, 159, 125, 2, 17, 0, 0, 6, 115, 223, 30, 72, 187, 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