Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb111c368f11dde9ce919758d6264f765eb05f026c015fc7d157f02e9e96964e

Tx prefix hash: 920e0541bdfc06883add4b7febb23c08a6e48166176edaaef4ea097e192f7701
Tx public key: 6f7cc1d00c2abe13e6c4a29f28b1820f976e08847663571909e7c96f44ea984c
Timestamp: 1735717258 Timestamp [UCT]: 2025-01-01 07:40:58 Age [y:d:h:m:s]: 00:167:15:16:32
Block: 1187724 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119522 RingCT/type: yes/0
Extra: 016f7cc1d00c2abe13e6c4a29f28b1820f976e08847663571909e7c96f44ea984c0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e8dbc549cf3d50020d88ce8e64496b2e43c14dfb27d356116f1ed9572c246cbb 0.600000000000 1674217 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": 1187734, "vin": [ { "gen": { "height": 1187724 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e8dbc549cf3d50020d88ce8e64496b2e43c14dfb27d356116f1ed9572c246cbb" } } ], "extra": [ 1, 111, 124, 193, 208, 12, 42, 190, 19, 230, 196, 162, 159, 40, 177, 130, 15, 151, 110, 8, 132, 118, 99, 87, 25, 9, 231, 201, 111, 68, 234, 152, 76, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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