Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd3b21cb399e23e4fe0e46616d31057435a2e9dbd3efb6e889e4f8673c3506d8

Tx prefix hash: 444c7e7f19f9611e4dcacba874bb6d6dbf3fd71fedc57a3ba24412153d1f1dd8
Tx public key: ba86b6dde86f9699cd9a40b2834cbd988443b4319c7ba806d0f70bd809cae91f
Timestamp: 1655900220 Timestamp [UCT]: 2022-06-22 12:17:00 Age [y:d:h:m:s]: 03:131:20:40:47
Block: 527922 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 873903 RingCT/type: yes/0
Extra: 01ba86b6dde86f9699cd9a40b2834cbd988443b4319c7ba806d0f70bd809cae91f021100000003a8c141c5000000000000000000

1 output(s) for total of 10.933908313000 dcy

stealth address amount amount idx
00: 1afc3f043d60667df12fcc9954cdbdc4dc3724ec91fe5069a3cdbbf8c2cb7cbc 10.933908313000 956663 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": 527932, "vin": [ { "gen": { "height": 527922 } } ], "vout": [ { "amount": 10933908313, "target": { "key": "1afc3f043d60667df12fcc9954cdbdc4dc3724ec91fe5069a3cdbbf8c2cb7cbc" } } ], "extra": [ 1, 186, 134, 182, 221, 232, 111, 150, 153, 205, 154, 64, 178, 131, 76, 189, 152, 132, 67, 180, 49, 156, 123, 168, 6, 208, 247, 11, 216, 9, 202, 233, 31, 2, 17, 0, 0, 0, 3, 168, 193, 65, 197, 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