Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: edb18bd500d705b86d5dceae6ec5c02dbf08dfdd5156b010df6fc92a9a5b1186

Tx prefix hash: fd84ed307d0575cfab1839ef578925ee897d614bf8b58c0186a5e212befda845
Tx public key: e0df2e2be744cc7266dcb8efd34221583013a575af7ce0cec9e473a924f490b0
Timestamp: 1738034614 Timestamp [UCT]: 2025-01-28 03:23:34 Age [y:d:h:m:s]: 00:140:17:57:00
Block: 1206670 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100529 RingCT/type: yes/0
Extra: 01e0df2e2be744cc7266dcb8efd34221583013a575af7ce0cec9e473a924f490b00211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f04a3772bf90b41e938e5dea279b991f35a5a7b58255d6caf235f0c4c6ab6011 0.600000000000 1693381 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": 1206680, "vin": [ { "gen": { "height": 1206670 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f04a3772bf90b41e938e5dea279b991f35a5a7b58255d6caf235f0c4c6ab6011" } } ], "extra": [ 1, 224, 223, 46, 43, 231, 68, 204, 114, 102, 220, 184, 239, 211, 66, 33, 88, 48, 19, 165, 117, 175, 124, 224, 206, 201, 228, 115, 169, 36, 244, 144, 176, 2, 17, 0, 0, 0, 3, 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