Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa97871d6b9f807387b68698f9a5b692ae3f60b1e1a67fedf4a5d6cf38dea3e9

Tx prefix hash: 8f96395cc0efd4b9bf1aa900df088fd50666bd9d875d6d20e140d6395fe7aae8
Tx public key: bfdfb30ad86c385c7debb83f96925b7c41d23eb17a96fad01e321608fd1e7270
Timestamp: 1702219715 Timestamp [UCT]: 2023-12-10 14:48:35 Age [y:d:h:m:s]: 01:120:14:36:38
Block: 910143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 347339 RingCT/type: yes/0
Extra: 01bfdfb30ad86c385c7debb83f96925b7c41d23eb17a96fad01e321608fd1e727002110000000275e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 460e5c124af6f4c2d74ca9c5c4522f0b9ab8266a0de1a17989f5ea70dbc86995 0.600000000000 1367288 of 15

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": 910153, "vin": [ { "gen": { "height": 910143 } } ], "vout": [ { "amount": 600000000, "target": { "key": "460e5c124af6f4c2d74ca9c5c4522f0b9ab8266a0de1a17989f5ea70dbc86995" } } ], "extra": [ 1, 191, 223, 179, 10, 216, 108, 56, 92, 125, 235, 184, 63, 150, 146, 91, 124, 65, 210, 62, 177, 122, 150, 250, 208, 30, 50, 22, 8, 253, 30, 114, 112, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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