Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c7f68eb495120e186d329283a4bc182ee60ec404bd66e1cee274baa1c76bb97

Tx prefix hash: 76e9350fbf3f643a61ff7d8621050d6a0eb3e5b1e9e7d129922d8e63a85551b0
Tx public key: 60d50be9c93635812d275fdb30ae72521abf0fc71a99df2dfe7ccdf6f3e959d4
Timestamp: 1717316837 Timestamp [UCT]: 2024-06-02 08:27:17 Age [y:d:h:m:s]: 00:302:21:04:03
Block: 1035320 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216448 RingCT/type: yes/0
Extra: 0160d50be9c93635812d275fdb30ae72521abf0fc71a99df2dfe7ccdf6f3e959d402110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3c732b2fac25a8e1f9791aa92ee35f8aa155d9cc3996be876843c951f4a89cd9 0.600000000000 1503841 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": 1035330, "vin": [ { "gen": { "height": 1035320 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c732b2fac25a8e1f9791aa92ee35f8aa155d9cc3996be876843c951f4a89cd9" } } ], "extra": [ 1, 96, 213, 11, 233, 201, 54, 53, 129, 45, 39, 95, 219, 48, 174, 114, 82, 26, 191, 15, 199, 26, 153, 223, 45, 254, 124, 205, 246, 243, 233, 89, 212, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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