Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35e998cef7a6951fff0ae5c4b2aae97069bedcc21017df8c89a19ddbbb003cf7

Tx prefix hash: abd08ac79a85c817d80d3178a32f93259dc9785780fd92f4c443914f71a3d5b6
Tx public key: 5a3f131944ffc783704a1f9bcb33666a73e910637f3938c71c2c60803c5139bf
Timestamp: 1745579080 Timestamp [UCT]: 2025-04-25 11:04:40 Age [y:d:h:m:s]: 00:210:06:15:00
Block: 1269109 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147981 RingCT/type: yes/0
Extra: 015a3f131944ffc783704a1f9bcb33666a73e910637f3938c71c2c60803c5139bf0211000000026c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8d984a2e012398c57245f30f04263b086cdc6bc38d96bc7cc2113baf6a9abdbe 0.600000000000 1756344 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": 1269119, "vin": [ { "gen": { "height": 1269109 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8d984a2e012398c57245f30f04263b086cdc6bc38d96bc7cc2113baf6a9abdbe" } } ], "extra": [ 1, 90, 63, 19, 25, 68, 255, 199, 131, 112, 74, 31, 155, 203, 51, 102, 106, 115, 233, 16, 99, 127, 57, 56, 199, 28, 44, 96, 128, 60, 81, 57, 191, 2, 17, 0, 0, 0, 2, 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