Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b40afb069e25ff76459c95cb5025076537cab4b2389f13c1b9eaf727fede7b13

Tx prefix hash: ee61dbd9f8305417d3867d9ccc5ad4bdc031ff0bda88ff3b975bb970c307390a
Tx public key: 074cfe4e2cc1e993815481ca1126ee4dfb8d6ab6f7b7c1a125253bbaeeadcfa4
Timestamp: 1583891819 Timestamp [UCT]: 2020-03-11 01:56:59 Age [y:d:h:m:s]: 04:327:23:54:38
Block: 80176 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1129287 RingCT/type: yes/0
Extra: 01074cfe4e2cc1e993815481ca1126ee4dfb8d6ab6f7b7c1a125253bbaeeadcfa402110000000128db8c57000000000000000000

1 output(s) for total of 332.923474977000 dcy

stealth address amount amount idx
00: e9c7a7e88d5fbfd9b8334063ba6e9f1bffd74df3b614ed49c2f50f652bc70cc8 332.923474977000 146724 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": 80186, "vin": [ { "gen": { "height": 80176 } } ], "vout": [ { "amount": 332923474977, "target": { "key": "e9c7a7e88d5fbfd9b8334063ba6e9f1bffd74df3b614ed49c2f50f652bc70cc8" } } ], "extra": [ 1, 7, 76, 254, 78, 44, 193, 233, 147, 129, 84, 129, 202, 17, 38, 238, 77, 251, 141, 106, 182, 247, 183, 193, 161, 37, 37, 59, 186, 238, 173, 207, 164, 2, 17, 0, 0, 0, 1, 40, 219, 140, 87, 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