Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 852379b8511060c87bce4ba5ab9a29f7a303e4f45b793a3db2a4fe7fbc72d955

Tx prefix hash: e7d5c76b35651acdbf9fbcd8113171966c7faf45afb5ef3e669503052af03521
Tx public key: 2d40658db7f843a4cc8d2c53a60b5268ff528000088b83626dfaf74a78f85c94
Timestamp: 1727567268 Timestamp [UCT]: 2024-09-28 23:47:48 Age [y:d:h:m:s]: 00:116:00:02:15
Block: 1120296 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82898 RingCT/type: yes/0
Extra: 012d40658db7f843a4cc8d2c53a60b5268ff528000088b83626dfaf74a78f85c9402110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a75026e62b85041b702d9c3452d75d86a7d3b25c1bed6eda2a2c5784374e7f46 0.600000000000 1602161 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": 1120306, "vin": [ { "gen": { "height": 1120296 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a75026e62b85041b702d9c3452d75d86a7d3b25c1bed6eda2a2c5784374e7f46" } } ], "extra": [ 1, 45, 64, 101, 141, 183, 248, 67, 164, 204, 141, 44, 83, 166, 11, 82, 104, 255, 82, 128, 0, 8, 139, 131, 98, 109, 250, 247, 74, 120, 248, 92, 148, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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