Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2dabe46a4bdc5c13cab0c1ccb0b87b19d5fb0fcbe966bccb26b2af4bbd955961

Tx prefix hash: 98d036c4a192b442708ec67d1e371e50de581f844cd97b34be6956ef32e51cba
Tx public key: ea3fbf40a427ac89d192e3c4c0243070e6047915babe2b01049a98ea74d7efcd
Timestamp: 1742505998 Timestamp [UCT]: 2025-03-20 21:26:38 Age [y:d:h:m:s]: 00:092:06:37:31
Block: 1243681 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65824 RingCT/type: yes/0
Extra: 01ea3fbf40a427ac89d192e3c4c0243070e6047915babe2b01049a98ea74d7efcd021100000008ed95dce7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d3b0f53a84d203e23369c648e2509030b989c25a3c5b4b9f18e4553f97affc77 0.600000000000 1730668 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": 1243691, "vin": [ { "gen": { "height": 1243681 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d3b0f53a84d203e23369c648e2509030b989c25a3c5b4b9f18e4553f97affc77" } } ], "extra": [ 1, 234, 63, 191, 64, 164, 39, 172, 137, 209, 146, 227, 196, 192, 36, 48, 112, 230, 4, 121, 21, 186, 190, 43, 1, 4, 154, 152, 234, 116, 215, 239, 205, 2, 17, 0, 0, 0, 8, 237, 149, 220, 231, 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