Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43c8c95883f4646c46d71b6961f43868479be962689fc1e503cf3a92d9fc0517

Tx prefix hash: 165174c67c3e12d9f883729d7f7f110dfebe862a0f3556a5b8032e648bab4f5e
Tx public key: a01d26d34e6f6ecd2f339c8feca9acf5e552c0ca033dae04fc451715244179a1
Timestamp: 1756117248 Timestamp [UCT]: 2025-08-25 10:20:48 Age [y:d:h:m:s]: 00:087:21:24:51
Block: 1354071 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 62729 RingCT/type: yes/0
Extra: 01a01d26d34e6f6ecd2f339c8feca9acf5e552c0ca033dae04fc451715244179a10211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e5e3ecefbd87a82f85b902dd3a036458b31034d5ad2e3c55bbcd585a4a6bdc94 0.600000000000 1842052 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": 1354081, "vin": [ { "gen": { "height": 1354071 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5e3ecefbd87a82f85b902dd3a036458b31034d5ad2e3c55bbcd585a4a6bdc94" } } ], "extra": [ 1, 160, 29, 38, 211, 78, 111, 110, 205, 47, 51, 156, 143, 236, 169, 172, 245, 229, 82, 192, 202, 3, 61, 174, 4, 252, 69, 23, 21, 36, 65, 121, 161, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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