Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f49bd63ce6da99f9fdb261189c0e91cd0859b3229fefda3b598491a1513c39c5

Tx prefix hash: 1838300fa09ebc13c2be7849aadb1c0b73e11e2aad2ede0ce8bbc14883191d45
Tx public key: 94a1c7c2f9bfb5f8546c6391e8ddc8d98f313d201bc42e40bacda42c8e42a17a
Timestamp: 1756077945 Timestamp [UCT]: 2025-08-24 23:25:45 Age [y:d:h:m:s]: 00:093:15:12:16
Block: 1353740 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66856 RingCT/type: yes/0
Extra: 0194a1c7c2f9bfb5f8546c6391e8ddc8d98f313d201bc42e40bacda42c8e42a17a0211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8ce4ca55407c99cb764e70b55ff241165f72900a6b5b22218aa06a1932a9d67a 0.600000000000 1841717 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": 1353750, "vin": [ { "gen": { "height": 1353740 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8ce4ca55407c99cb764e70b55ff241165f72900a6b5b22218aa06a1932a9d67a" } } ], "extra": [ 1, 148, 161, 199, 194, 249, 191, 181, 248, 84, 108, 99, 145, 232, 221, 200, 217, 143, 49, 61, 32, 27, 196, 46, 64, 186, 205, 164, 44, 142, 66, 161, 122, 2, 17, 0, 0, 0, 2, 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