Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 868d09dd160b51823029c58035cc31401fcb510c6e639d1f50850de3a1fee3c3

Tx prefix hash: e7396e0ca8254d771b573083425feaed70a73e536b088349ea74779e8ddf37d5
Tx public key: 700db24ee8725284d51133607df8c5088eed533dbf5ae2202ec3a10dae7aed68
Timestamp: 1700892161 Timestamp [UCT]: 2023-11-25 06:02:41 Age [y:d:h:m:s]: 01:145:11:23:52
Block: 899138 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365153 RingCT/type: yes/0
Extra: 01700db24ee8725284d51133607df8c5088eed533dbf5ae2202ec3a10dae7aed6802110000000575e3f0e9000000000000000000

1 output(s) for total of 0.643846799000 dcy

stealth address amount amount idx
00: 1b9b2a0c743210600f5663a06a4e0e874fbfe15030de26377ea2524b4172d8cb 0.643846799000 1355581 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": 899148, "vin": [ { "gen": { "height": 899138 } } ], "vout": [ { "amount": 643846799, "target": { "key": "1b9b2a0c743210600f5663a06a4e0e874fbfe15030de26377ea2524b4172d8cb" } } ], "extra": [ 1, 112, 13, 178, 78, 232, 114, 82, 132, 213, 17, 51, 96, 125, 248, 197, 8, 142, 237, 83, 61, 191, 90, 226, 32, 46, 195, 161, 13, 174, 122, 237, 104, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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