Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dda563d198a7058dc9ab8758e2bac0e86e667593badebc978d6d2460644b0965

Tx prefix hash: bcefede78e8ac2d51481d185a45aac406827f03dc16e07a051dca4b3656f7ca1
Tx public key: bd33b0f51598c72e5aa91e7d70129317e72ef0d56e503dd65e142f1ac4659780
Timestamp: 1721823957 Timestamp [UCT]: 2024-07-24 12:25:57 Age [y:d:h:m:s]: 00:183:01:01:48
Block: 1072670 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130926 RingCT/type: yes/0
Extra: 01bd33b0f51598c72e5aa91e7d70129317e72ef0d56e503dd65e142f1ac465978002110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1cd1cccdcb93cf655bb9915689b0cb421983a8f328bd5c872a4bb4869cdb3e5 0.600000000000 1545157 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": 1072680, "vin": [ { "gen": { "height": 1072670 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1cd1cccdcb93cf655bb9915689b0cb421983a8f328bd5c872a4bb4869cdb3e5" } } ], "extra": [ 1, 189, 51, 176, 245, 21, 152, 199, 46, 90, 169, 30, 125, 112, 18, 147, 23, 231, 46, 240, 213, 110, 80, 61, 214, 94, 20, 47, 26, 196, 101, 151, 128, 2, 17, 0, 0, 0, 10, 233, 20, 221, 21, 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