Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50f7a4ec5d0763f8bac63dfc7f953a4987f0e24ee07d33ab56e65026832cb9a5

Tx prefix hash: 743d1aa388c4777e5252196dfd75b7611e5fffb148cdc9c09c67ced954eeaa7f
Tx public key: ea6b22c239673e38fdc0cba8f4d41366d9f1079520e2a0ee1b106968f3d53fbf
Timestamp: 1695597396 Timestamp [UCT]: 2023-09-24 23:16:36 Age [y:d:h:m:s]: 01:195:05:16:42
Block: 855446 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 400575 RingCT/type: yes/0
Extra: 01ea6b22c239673e38fdc0cba8f4d41366d9f1079520e2a0ee1b106968f3d53fbf0211000000084b8f5122000000000000000000

1 output(s) for total of 0.898570875000 dcy

stealth address amount amount idx
00: f2c8f96616008e00e9106946a7b090736b0162719ffe9cf4fee9f53bc04b103e 0.898570875000 1309468 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": 855456, "vin": [ { "gen": { "height": 855446 } } ], "vout": [ { "amount": 898570875, "target": { "key": "f2c8f96616008e00e9106946a7b090736b0162719ffe9cf4fee9f53bc04b103e" } } ], "extra": [ 1, 234, 107, 34, 194, 57, 103, 62, 56, 253, 192, 203, 168, 244, 212, 19, 102, 217, 241, 7, 149, 32, 226, 160, 238, 27, 16, 105, 104, 243, 213, 63, 191, 2, 17, 0, 0, 0, 8, 75, 143, 81, 34, 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