Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b66db1ffeb45714a512210f14308c268e5717272f8fd3ec331d9475b6b44c4b4

Tx prefix hash: bf0841ca7e143136b399133dabeaedfe574cdbf86edbe652207b58b298e5a7d8
Tx public key: 1ea25a3b839bfb223ff2c42adc45cc8e74a8410e8edc9832c808652497881cdb
Timestamp: 1736409908 Timestamp [UCT]: 2025-01-09 08:05:08 Age [y:d:h:m:s]: 00:160:04:17:48
Block: 1193460 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114196 RingCT/type: yes/0
Extra: 011ea25a3b839bfb223ff2c42adc45cc8e74a8410e8edc9832c808652497881cdb02110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2d5c011eb897ba0aa1d300003d9713609536532dc9ffa4add9a4040d3a0ee28 0.600000000000 1680021 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": 1193470, "vin": [ { "gen": { "height": 1193460 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2d5c011eb897ba0aa1d300003d9713609536532dc9ffa4add9a4040d3a0ee28" } } ], "extra": [ 1, 30, 162, 90, 59, 131, 155, 251, 34, 63, 242, 196, 42, 220, 69, 204, 142, 116, 168, 65, 14, 142, 220, 152, 50, 200, 8, 101, 36, 151, 136, 28, 219, 2, 17, 0, 0, 0, 10, 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