Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed0283bc64caf96dc2caed79ec8b42ad9fc0abf61bf306460da44befe265d88c

Tx prefix hash: ec0f058dd2680815dc308d46f74c02bcf893cd06a4c328956ec1b83e92dede90
Tx public key: f354179f3601a4e60232a8a7eb36f1e5c349f57723d210877d19029610b0b4f6
Timestamp: 1744868451 Timestamp [UCT]: 2025-04-17 05:40:51 Age [y:d:h:m:s]: 00:257:02:08:57
Block: 1263211 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181533 RingCT/type: yes/0
Extra: 01f354179f3601a4e60232a8a7eb36f1e5c349f57723d210877d19029610b0b4f6021100000003dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af0cf0c05411a3b5c362953c1465ef3bd1a1bfa614e517a013ce62f56c2a6d12 0.600000000000 1750396 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": 1263221, "vin": [ { "gen": { "height": 1263211 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af0cf0c05411a3b5c362953c1465ef3bd1a1bfa614e517a013ce62f56c2a6d12" } } ], "extra": [ 1, 243, 84, 23, 159, 54, 1, 164, 230, 2, 50, 168, 167, 235, 54, 241, 229, 195, 73, 245, 119, 35, 210, 16, 135, 125, 25, 2, 150, 16, 176, 180, 246, 2, 17, 0, 0, 0, 3, 219, 181, 113, 193, 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