Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e89d288e91829b9607b872e017a0a0f26b0a0aeb9ced474648e7ae679deb6f04

Tx prefix hash: fb9e93da0981e49befe0e060b0165f3ca57a24faa37670d008e1b80e5590f7d6
Tx public key: 33243be97293ac1747c2cc39c14568e6a308e9fffe9d74385e66a7f9715a89b2
Timestamp: 1681718149 Timestamp [UCT]: 2023-04-17 07:55:49 Age [y:d:h:m:s]: 01:271:00:06:21
Block: 740421 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 455185 RingCT/type: yes/0
Extra: 0133243be97293ac1747c2cc39c14568e6a308e9fffe9d74385e66a7f9715a89b2021100000002b3164c24000000000000000000

1 output(s) for total of 2.161116011000 dcy

stealth address amount amount idx
00: 93d4a826d9c4acbe077d2edc0a42140b64a05873535f571bc40c42c97b6924ca 2.161116011000 1187316 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": 740431, "vin": [ { "gen": { "height": 740421 } } ], "vout": [ { "amount": 2161116011, "target": { "key": "93d4a826d9c4acbe077d2edc0a42140b64a05873535f571bc40c42c97b6924ca" } } ], "extra": [ 1, 51, 36, 59, 233, 114, 147, 172, 23, 71, 194, 204, 57, 193, 69, 104, 230, 163, 8, 233, 255, 254, 157, 116, 56, 94, 102, 167, 249, 113, 90, 137, 178, 2, 17, 0, 0, 0, 2, 179, 22, 76, 36, 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