Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88e598680eeeedf9b9e1c0ad8d2ff4a8d22c142ff67586c6ddbb2e4a35eacd9e

Tx prefix hash: f74bd8c4c6cf5bee817213217adb5efc97a71fd0386c8de1111f9dbdc69129d6
Tx public key: 0f1cc8396d18a0e8b4023af955cbd035ed1942c4c1abd3453cc6ec336bac1183
Timestamp: 1749815393 Timestamp [UCT]: 2025-06-13 11:49:53 Age [y:d:h:m:s]: 00:160:05:52:16
Block: 1304115 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112274 RingCT/type: yes/0
Extra: 010f1cc8396d18a0e8b4023af955cbd035ed1942c4c1abd3453cc6ec336bac118302110000000343846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ac8cd4be1e52dcab927fdfe485f1dad10cb66205b3e57d8bfd9b6b8ec08bb44 0.600000000000 1791702 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": 1304125, "vin": [ { "gen": { "height": 1304115 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ac8cd4be1e52dcab927fdfe485f1dad10cb66205b3e57d8bfd9b6b8ec08bb44" } } ], "extra": [ 1, 15, 28, 200, 57, 109, 24, 160, 232, 180, 2, 58, 249, 85, 203, 208, 53, 237, 25, 66, 196, 193, 171, 211, 69, 60, 198, 236, 51, 107, 172, 17, 131, 2, 17, 0, 0, 0, 3, 67, 132, 109, 102, 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