Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8399ca5735c59d3817e6df9453c25720a958aacb72f530c58488d111a459eda8

Tx prefix hash: 7bd0c65ce509d52111c2b6ec82110ffbe532a0cbc0d49ed098060649d31cb6f0
Tx public key: 67f536b73fc8e1f18b0af9cf7b1f56d57e27d216d9b14a7d9c3dfd0d09cb41c5
Timestamp: 1744300910 Timestamp [UCT]: 2025-04-10 16:01:50 Age [y:d:h:m:s]: 00:223:14:49:04
Block: 1258519 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157547 RingCT/type: yes/0
Extra: 0167f536b73fc8e1f18b0af9cf7b1f56d57e27d216d9b14a7d9c3dfd0d09cb41c50211000000066c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a168c35243786e653e09c35c559efa41ab75afbd3a63d55c703e9ee4b1d675c8 0.600000000000 1745652 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": 1258529, "vin": [ { "gen": { "height": 1258519 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a168c35243786e653e09c35c559efa41ab75afbd3a63d55c703e9ee4b1d675c8" } } ], "extra": [ 1, 103, 245, 54, 183, 63, 200, 225, 241, 139, 10, 249, 207, 123, 31, 86, 213, 126, 39, 210, 22, 217, 177, 74, 125, 156, 61, 253, 13, 9, 203, 65, 197, 2, 17, 0, 0, 0, 6, 108, 152, 170, 61, 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