Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d40a511be23abcd8bafc3f6b73b67db1d077a2a341a14d181791603ab7ac189f

Tx prefix hash: 85aa9530bf5fafd0a72c10a65fe7dfc783cccea66b08bf1cb3e0fb5e9bf130e5
Tx public key: f0c25b76e3d7a8a57bc795d67ac52f75e9b181e7561dabc1672010dac2acefe2
Timestamp: 1754649264 Timestamp [UCT]: 2025-08-08 10:34:24 Age [y:d:h:m:s]: 00:099:17:56:41
Block: 1342762 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70377 RingCT/type: yes/0
Extra: 01f0c25b76e3d7a8a57bc795d67ac52f75e9b181e7561dabc1672010dac2acefe2021100000003dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2b6ed21764d8b31d745713eb076f1a85e9cfebafe43f38f85b8b16c3279d61de 0.600000000000 1830595 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": 1342772, "vin": [ { "gen": { "height": 1342762 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b6ed21764d8b31d745713eb076f1a85e9cfebafe43f38f85b8b16c3279d61de" } } ], "extra": [ 1, 240, 194, 91, 118, 227, 215, 168, 165, 123, 199, 149, 214, 122, 197, 47, 117, 233, 177, 129, 231, 86, 29, 171, 193, 103, 32, 16, 218, 194, 172, 239, 226, 2, 17, 0, 0, 0, 3, 223, 195, 186, 73, 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